2017-03-15 - 21711 - Spec - Invoice Output - Correct Key Combination (Pierre by 2017-12-30) #Billing #invoices #EMEA

SPECIFICATIONS

21711 - Spec - Invoice Output - Correct Key Combination


Purpose


Invoice output - correct key combination.

Admin Info


Purpose
Invoice output - correct key combination
Requested By
Pierre Pazgrat
Spec Created By
Surya Basa
Spec Created Date
04/03/2017
Spec QA by
Surya Basa
Objects
V_T682
RVCOMFZZ
ZKOMKBV3
Document Status
Complete


Estimates



Sl.No
Activity
Estimation in Hours
1
Research
02
2
Documentation
02
3
Development/ Config
14
4
Unit test in DEV
02
5
Unit test in QUA
02
6
Other activity


TOTAL
22

References


Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

NA

Documents

[Attach any document(s) received for the requirement(s)]

Invoice Output - Key Combination.docx


Spec Changes


[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.
Change Details
Requested By
Requested On
Notes if any

























Functional Requirement


Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]

A mistake has been made when implementing a new key combination for the invoice output. This topic aims at correcting the mistake.

In Scope:

[List the activities to be included in scope]

The change is only for the output type ZRD8 and EMEA.

Out of Scope:

[Out of scope activities]

Output print outputs are out of scope.

Solution Summary


[Discuss this section with Requester and get approval prior to beginning work]

- The config changes are to be made as specified in the attached document.
- The output communication structures (KOMKBV3) should be added with the new field for credit rep (SBGRP) and the field should be filled in the user exit (RVCOMFZZ).


Test Plan

[List test scenarios/cases to be executed here]
Test ID
Test Scenario
Expected Results
SD001
Condition record - Yes
Credit Rep assigned - Yes
ZRD8 print output should trigger
SD002
Condition record - Yes
Credit Rep assigned - No
ZRD8 print output shouldn't trigger
SD003
Condition record - No
Credit Rep assigned - Yes
ZRD8 print output shouldn't trigger
SD004
Condition record - No
Credit Rep assigned - No
ZRD8 print output shouldn't trigger

Solution Details


[Provide complete technical details for configuration or programming here]

1. In NACE transaction, replace key combination sales org/bill to/cred rep with sales org/bill type/credit rep in the access sequence 0004 (sales org/customer).

Credit Rep.PNG

Issues


[List Issues / Bugs identified in configuration or development]

1. Table 510 didn't exist in the destination environment. Hence, there was an error while maintaining condition records. 510 was replaced with 507 with the same key combination and outputs were tested.